Method and system for merchant debit routing table change detection

ABSTRACT

A method for identifying a merchant debit routing table includes: storing a plurality of transaction data entries, each entry including a first and second debit network, a utilized network, a merchant identifier, and a transaction date, the utilized network being the first or second debit network; receiving a routing identification request, the request including a merchant identification; identifying a merchant transaction group, the group including entries where the merchant identifier corresponds to the merchant identification; identifying a plurality of network subgroups in the group, each subgroup including entries including a common first and second debit network; identifying, for each subgroup, a preferred network based on the utilized network for each entry in the subgroup where the transaction date is a specific date; and identifying a routing table for a merchant associated with the merchant identifier based on the preferred network and the first and second debit network for each subgroup.

FIELD

The present disclosure relates to the detection of merchant debitrouting tables, specifically the detection of merchant debit routingtables based on available debit card routing networks and debittransaction routing history.

BACKGROUND

Debit cards are traditionally eligible for processing using one of two,or sometimes more, debit networks. When a consumer uses a debit card tofund a financial transaction, the merchant is often responsible forselecting which eligible debit network is to be used for processing.Merchants many times select a debit network based on the expense chargedby the network for processing the transaction and for the routing of thetransaction to the network itself. In some instances, a merchant mayselect a network based on convenience. Due to the volume of debittransactions for many retailers, merchants typically use a routingtable, which sets a priority debit networks to be used, such that thehighest (most preferred) debit network is always used if available, andcontinuing down to the first available network if the highest or nexthighest is unavailable.

Accordingly, many debit networks may desire to identify their positionin a merchant's routing table. However, pricing structures andcircumstances frequently change, which many times result in merchantsand retailers modifying their routing table accordingly. For merchantsthat process debit transactions funded by debit cards associated with alarge number of different debit networks, pricing structures and networkconfigurations may change frequently. This may result in a debit routingtable that changes the order of its network preferences often.Therefore, while a debit network may eventually discover their positionin a merchant's routing table, such information may become outdated assoon as a merchant makes a modification to their table.

Thus, there is need for a technical solution to detecting changes in amerchant's debit routing table.

SUMMARY

The present disclosure provides a description of a systems and methodsfor the identification of merchant debit routing tables.

A method for identifying a merchant debit routing table includes:storing, in a database, a plurality of transaction data entries, whereineach transaction data entry includes data related to a financialtransaction and includes at least a first debit network, a second debitnetwork, a utilized debit network, a merchant identifier, and atransaction date, the utilized debit network being the first debitnetwork or the second debit network; receiving, by a receiving device, arouting identification request, wherein the routing identificationrequest includes at least a merchant identification; identifying, by aprocessing device, a merchant transaction group, wherein the merchanttransaction group includes transaction data entries of the plurality oftransaction data entries where the included merchant identifiercorresponds to the merchant identification; identifying, by a processingdevice, a plurality of network subgroups in the merchant transactiongroup, wherein each network subgroup includes transaction data entriesincluded in the merchant transaction group including a common firstdebit network and a common second debit network; identifying, for eachnetwork subgroup of the plurality of network subgroups, a preferreddebit network based on the utilized debit network for each transactiondata entry in the network subgroup where the transaction date is aspecific date; and identifying, by the processing device, a routingtable for a merchant associated with the merchant identifier based onthe preferred debit network and the first debit network and the seconddebit network for each network subgroup of the plurality of networksubgroups.

Another method for identifying a merchant debit routing table includes:storing, in a database, a plurality of transaction data entries, whereineach transaction data entry includes data related to a financialtransaction and includes at least a first debit network, a second debitnetwork, a utilized debit network, a merchant identifier, and atransaction date, the utilized debit network being the first debitnetwork or the second debit network; receiving, by a receiving device, arouting identification request, wherein the routing identificationrequest includes at least a merchant identification; identifying, by aprocessing device, a merchant transaction group, wherein the merchanttransaction group includes transaction data entries of the plurality oftransaction data entries where the included merchant identifiercorresponds to the merchant identification; identifying, by a processingdevice, a plurality of network subgroups in the merchant transactiongroup, wherein each network subgroup includes transaction data entriesincluded in the merchant transaction group including a common firstdebit network and a common second debit network; identifying, for eachdate of a predetermined range of dates, a preferred debit network foreach network subgroup of the plurality of network subgroups based on theutilized debit network for each transaction data entry in the networksubgroup where the transaction date is a specific date; identifying, foreach date of the predetermined range of dates, a routing table for amerchant associated with the merchant identifier based on the preferreddebit network and the first debit network and the second debit networkfor each network subgroup of the plurality of network subgroups for therespective date of the predetermined range of dates; and identifying, bythe processing device, a change in debit routing for the merchant basedon the routing table for the merchant for each date of the predeterminedrange of dates.

A system for identifying a merchant debit routing table includes adatabase, a receiving device, and a processing device. The database isconfigured to store a plurality of transaction data entries, whereineach transaction data entry includes data related to a financialtransaction and includes at least a first debit network, a second debitnetwork, a utilized debit network, a merchant identifier, and atransaction date, the utilized debit network being the first debitnetwork or the second debit network. The receiving device is configuredto receive a routing identification request, wherein the routingidentification request includes at least a merchant identification. Theprocessing device is configured to: identify a merchant transactiongroup, wherein the merchant transaction group includes transaction dataentries of the plurality of transaction data entries where the includedmerchant identifier corresponds to the merchant identification; identifya plurality of network subgroups in the merchant transaction group,wherein each network subgroup includes transaction data entries includedin the merchant transaction group including a common first debit networkand a common second debit network; identify, for each network subgroupof the plurality of network subgroups, a preferred debit network basedon the utilized debit network for each transaction data entry in thenetwork subgroup where the transaction date is a specific date; andidentify a routing table for a merchant associated with the merchantidentifier based on the preferred debit network and the first debitnetwork and the second debit network for each network subgroup of theplurality of network subgroups.

Another system for identifying a merchant debit routing table includes adatabase, a receiving device, and a processing device. The database isconfigured to store a plurality of transaction data entries, whereineach transaction data entry includes data related to a financialtransaction and includes at least a first debit network, a second debitnetwork, a utilized debit network, a merchant identifier, and atransaction date, the utilized debit network being the first debitnetwork or the second debit network. The receiving device is configuredto receive a routing identification request, wherein the routingidentification request includes at least a merchant identification. Theprocessing device is configured to: identify a merchant transactiongroup, wherein the merchant transaction group includes transaction dataentries of the plurality of transaction data entries where the includedmerchant identifier corresponds to the merchant identification; identifya plurality of network subgroups in the merchant transaction group,wherein each network subgroup includes transaction data entries includedin the merchant transaction group including a common first debit networkand a common second debit network; identify, for each date of apredetermined range of dates, a preferred debit network for each networksubgroup of the plurality of network subgroups based on the utilizeddebit network for each transaction data entry in the network subgroupwhere the transaction date is a specific date; identify, for each dateof the predetermined range of dates, a routing table for a merchantassociated with the merchant identifier based on the preferred debitnetwork and the first debit network and the second debit network foreach network subgroup of the plurality of network subgroups for therespective date of the predetermined range of dates; and identify achange in debit routing for the merchant based on the routing table forthe merchant for each date of the predetermined range of dates.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The scope of the present disclosure is best understood from thefollowing detailed description of exemplary embodiments when read inconjunction with the accompanying drawings. Included in the drawings arethe following figures:

FIG. 1 is a high level architecture illustrating a system for theidentification of merchant debit routing tables and changes therein.

FIG. 2 is a block diagram illustrating an embodiment of a processingserver for use in the system of FIG. 1 in accordance with exemplaryembodiments.

FIG. 3 is a block diagram illustrating a transaction database of theprocessing server of FIG. 2 in accordance with exemplary embodiments.

FIGS. 4-6 are diagrams illustrating an example data set of thetransaction database of FIG. 3 and a method for identifying a merchantdebit routing table using the data set in accordance with exemplaryembodiments.

FIG. 7 is a diagram illustrating identification of changes in a merchantdebit routing table in accordance with exemplary embodiments.

FIGS. 8 and 9 are flow charts illustrating exemplary methods foridentifying merchant debit routing tables in accordance with exemplaryembodiments.

FIG. 10 is a block diagram illustrating computer system architecture inaccordance with exemplary embodiments.

Further areas of applicability of the present disclosure will becomeapparent from the detailed description provided hereinafter. It shouldbe understood that the detailed description of exemplary embodiments areintended for illustration purposes only and are, therefore, not intendedto necessarily limit the scope of the disclosure.

DETAILED DESCRIPTION Definition of Terms

Debit Network—A system or network used for the transfer of money via theuse of a debit card. Debit networks may use a variety of differentprotocols and procedures in order to process the transfer of money forvarious types of debit transactions. Debit networks may chargeprocessing fees or other types of fees for the processing of a debittransaction to a merchant or acquirer from which the debit transactionis routed. Examples of networks or systems configured to perform asdebit networks include Maestro, ACCEL, Interlink, MAC, MoneyPass, Pulse,SHAZAM, STAR, etc.

Payment Account—A financial account that may be used to fund atransaction, such as a checking account, savings account, creditaccount, virtual payment account, etc. A payment account may beassociated with an entity, which may include a person, family, company,corporation, governmental entity, etc. In some instances, a paymentaccount may be virtual, such as those accounts operated by PayPal®, etc.

Debit Card—A card or data associated with a payment account that may beprovided to a merchant in order to fund a financial transaction via theassociated payment account. A debit card may be a physical card that maybe provided to a merchant, or may be data representing the associatedpayment account (e.g., as stored in a communication device, such as asmart phone or computer). For example, in some instances, data includinga payment account number may be considered a debit card for theprocessing of a transaction funded by the associated payment account. Adebit card may differ from other types of payment cards (e.g., a creditcard) in networks that are used to process transactions involving thecard and that, for debit card transactions, funds are immediatelytransferred from the corresponding payment account to fund thetransaction.

System for Identifying Merchant Debit Routing Tables

FIG. 1 is a block diagram illustrating a system 100 for identifyingmerchant debit routing tables and identifying changes in merchant debitrouting tables.

The system 100 may include a consumer 102. The consumer 102 may have adebit card 104 issued to the consumer 102 by an issuer 106, such as anissuing bank. The consumer 102 may have a payment account with theissuer 106, and the debit card 104 may be associated with that paymentaccount. The consumer 102 may use the debit card 104 at a merchant 108to fund a financial transaction. As used herein, the term “merchant” mayrefer to an entity (e.g., a person, company, partnership, holdingcompany, etc.) with which the consumer 102 may transact, may refer to aspecific location (e.g., a physical location at which the consumertransacts), or may refer to a point-of-sale system used to conduct(e.g., enter, initiate, process, finalize, etc.) the financialtransaction. The merchant 108 may enter transaction information and thepayment details (e.g., card details of the debit card 104) into thepoint of sale, and the merchant 108, or an acquirer (e.g., an acquiringbank) on behalf of the merchant 108, may submit an authorization requestfor the financial transaction to a debit network 110.

The debit network 110 may include one or more debit processor 112,illustrated as debit processors 112 a, 112 b, and 112 c. Each debitprocessor 112 may operate an independent debit network 110. In someinstances, the financial transaction may be routed to more than onedebit network 110 such that the financial transaction is processed bymultiple debit processors 112. The debit processor 112 may process thefinancial transaction funded by the debit card 104 using methods thatwill be apparent to persons having skill in the relevant art. Suchmethods may include transmitted relevant transaction information (e.g.,the account number corresponding to the debit card 104, transactionamount, etc.) to the issuer 106, which may identify the payment accountassociated with the debit card 104 and may return approval or denial tothe debit processor 112 based on the transaction amount and a balance ofthe payment account.

The debit processor 112 may transmit an authorization response to themerchant 108 and/or an acquirer via the debit network 110. The merchant108 may then finalize the transaction based on the authorizationresponse, such as by providing transacted for goods and/or services tothe consumer 102 upon approval of the transaction, or notifying theconsumer 102 of denial of the transaction.

In some embodiments, the debit card 104 may be associated with two ormore debit processors 112. In such an embodiment, the merchant 108 maysubmit an authorization request for the financial transaction to onlythose debit processors 112 associated with the debit card 104. Themerchant 108 (e.g., the point-of-sale system operated by the merchant108) may include a routing table, discussed in more detail below. Therouting table may indicate a priority of preference between debitprocessors 112, such that the merchant 108 may submit the authorizationrequest to the debit processor 112 and debit network 110 with thehighest priority in the routing table.

The system may also include a processing server 114. The processingserver 114 may be configured to store transaction data for a pluralityof financial transactions, as discussed in more detail below. In someembodiments, the processing server 114 may be a debit processor 112 andmay operate a debit network 110. In such an embodiment, the processingserver 114 may store transaction data for only those financialtransactions processed by the processing server 114. In some instances,the processing server 114 may receive transaction data for financialtransactions processed by other or multiple debt processors 112. Theprocessing server 114 may be configured to identify the debit routingtable for the merchant 108 based on the stored transaction data usingmethods as discussed below.

Processing Server

FIG. 2 illustrates an embodiment of the processing server 114 of thesystem 100. It will be apparent to persons having skill in the relevantart that the embodiment of the processing server 114 illustrated in FIG.2 is provided as illustration only and may not be exhaustive to allpossible configurations of the processing server 114 suitable forperforming the functions as discussed herein. For example, the computersystem 1000 illustrated in FIG. 10 and discussed in more detail belowmay be a suitable configuration of the processing server 114.

The processing server 114 may include a receiving unit 202. Thereceiving unit 202 may be configured to receive a routing identificationrequest including at least one merchant identification (e.g., associatedwith the merchant 108). The processing server 114 may also include aprocessing unit 204, which may be configured to identify the merchantidentification included in the routing identification request, and thenmay further identify a group of transaction data entries 120 in atransaction database 118 associated with financial transactionsinvolving the merchant 108 associated with the merchant identification.

The transaction data entries 120, discussed in more detail below withreference to FIG. 3, may include at least a first debit network and asecond debit network, and may further indicate a utilized debit network(e.g., debit network used for processing the associated financialtransaction). The processing unit 204 may be configured to identifying,in the group of transaction data entries 120, a plurality of networksubgroups, wherein the transaction data entries in each network subgroupincludes a common first debit network and a common second debit network.The processing unit 204 may then identify, for each network subgroup, apreferred debit network based on the indicated utilized debit network.Based on the identified preferred debit networks for each networksubgroup, the processing unit 204 may then identifying a routing tablefor the merchant 108.

The processing server 114 may further include a transmitting unit 206.The transmitting unit 206 may be configured to transmit the identifiedmerchant routing table in response to the routing identificationrequest. In some embodiments, the processing unit 204 may identify arouting table for the merchant 108 for each date of a specific listingof dates or period of time, and may further detect a change in themerchant routing table based on the identified routing tables. Such amethod, illustrated in more detail and discussed below with respect toFIGS. 4-7, may enable the processing server 114 to easily detect changesin a merchant routing table. In some instances, the processing server114 may identify a routing table for the merchant 108 each day based ontransaction data entries 120 related to transactions initiated on thatbusiness day or the preceding business day, which may enable theprocessing server 114 to identify a change in a routing table on orwithin close proximity to the day it occurs.

Transaction Database

FIG. 3 is an illustration of the transaction database 118. Thetransaction database 118 may include a plurality of transaction dataentries 120, illustrated in FIG. 3 as transaction data entries 120 a,120 b, and 120 c. Each transaction data entry 120 may include datarelated to a financial transaction and may include at least a firstdebit network 302, a second debit network 304, a utilized debt network308, a merchant identifier 310, and a transaction date 312.

The first debit network 302 and the second debit network 304 maycorrespond to a first and second debit network 110 for which the debitcard (e.g., the debit card 104) used in the related financialtransaction is eligible for processing. In some instances, the debitcard 104 may include a third debit network 306, which may be a thirddebit network 110 eligible for processing of the debit transactioninvolving the debit card 104.

The utilized debit network 308 may be the debit network 110 used toprocess the related financial transaction. It will be apparent topersons having skill in the relevant art that the utilized debit network308 in a transaction data entry 120 will be one of the first debitnetwork 302, second debit network 304, or, in instances where one ormore may be included, the third or fourth, etc., debit network 306. Insome embodiments, such as where the processing server 114 may be part ofor associated with a debit network 110, the transaction data entries 120included in the transaction database 118 may all include the sameutilized debit network 308 (e.g., which may be the debit network 110).

The merchant identifier 310 may be a unique value identifying a merchant(e.g., the merchant 108) involved in the related financial transaction.Values suitable for use as the merchant identifier 310 will be apparentto persons having skill in the relevant art, such as a merchantidentification number (MID). The merchant identifier 310 may be used inorder to identify a group of transaction data entries 120 related tofinancial transactions involving the same merchant 108, for use inidentifying the routing table for the involved merchant 108. Thetransaction date 312 may be the date on which the related financialtransaction was processed. It will be apparent to persons having skillin the relevant art that the transaction date 312 may correspond to thedate of authorization of the financial transaction, clearing of thefinancial transaction, or any other point in the processing cycle of afinancial transaction suitable for use in identifying a merchant routingtable.

In some embodiments, a transaction data entry 120 may further include atransaction amount 314. The transaction amount 314 may be used toseparate the transaction data entries 120 into further subgroups (e.g.,as discussed in more detail below) to identify multiple routing tablesfor a single merchant 108 dependent on transaction amount. For example,due to complex pricing structures, the merchant 108 may have a firstrouting table for all transactions under five dollars, and may have asecond routing table for all transactions five dollars or more. In someembodiments, the transaction amount 314 may be a transaction amountcategory (e.g., five dollars or less, between five and ten dollars,between ten and twenty dollars, etc.).

Identification of a Merchant Routing Table

FIGS. 4-7 illustrate exemplary data sets of transaction data entries 120in the transaction database 118 for use by the processing unit 204 inthe identification of a merchant routing table for a specific merchant(e.g., the merchant 108).

In order to identify a merchant routing table for a specific date, theprocessing unit 204 of the processing server 114 may identify atransaction dataset 402 for all transaction data entries 120 in thetransaction database 118 where the transaction date 312 is the specificdate. As illustrated in FIG. 4, the transaction dataset 402 may includeall transaction data entries 120 where the transaction date 312 is Jul.3, 2012.

The processing unit 204 may identify, from the transaction dataset 402,a merchant transaction group 404. The merchant transaction group 404 mayinclude all those transaction data entries 120 where the merchantidentifier 310 is a specific merchant identifier, such as a merchantidentification received in a routing identification request. Ininstances where the transaction dataset 402 may include transaction dataentries 120 including a plurality of transaction dates 312, theprocessing unit 204 may identify the merchant transaction group 404 oftransaction data entries 120 including both a common merchant identifier310 and transaction date 312, such as included in a routingidentification request, which may result in the merchant transactiongroup 404 illustrated in FIG. 4.

The processing unit 204 may then identify a plurality of networksubgroups 502 from the merchant transaction group 404, as illustrated inFIG. 5. The plurality of network subgroups 502 may include networksubgroups 504 wherein each network subgroup 504 includes transactiondata entries 120 including a common first debit network 302 and seconddebit network 304. It will be apparent to persons having skill in therelevant art that, in most instances, each network subgroup 504 willinclude a common utilized debit network 308. In instances where amerchant 108 may include multiple routing tables (e.g., based ontransaction amount 314), then each network subgroup 504 may includemultiple utilized debit networks 308, as discussed in more detail below.In some embodiments, each network subgroup 504 may further include anumber 506 of transaction data entries 120 included in the networksubgroup.

It will be further apparent to persons having skill in the relevant artthat, in some instances, such as where the processing server 114 may beincluded in or associated with a specific debit processor 112 or debitnetwork 110, the network subgroups 504 may each include the specificdebit network 110 corresponding to the specific debit processor 112 asthe utilized debit network 308. In such instances, the first debitnetwork 302 or the second debit network 304 (e.g., or the third debitnetwork 306 in instances where the debit cards 104 used in transactionsin a network subgroup 504 have at least three eligible debit networks110) may be the specific debit network 110. It will be apparent topersons having skill in the relevant art that such data may not precludethe processing server 114 from identifying the merchant routing table.

The processing unit 204 may then use the plurality of network subgroups502 to identify a merchant routing table 602 for the merchant 108, asillustrated in FIG. 6. The merchant routing table 602 may include aplurality of debit processors 112 listed in order of the preference ofthe merchant 108 in routing debit transactions. The merchant routingtable 602 may be ordered based on the utilized debit network 308 foreach network subgroup 504 of the plurality of network subgroups 502,along with the first debit network 302 and the second debit network 304for the network subgroup 504. For example, as illustrated in FIG. 6, ineach instance where Maestro is an eligible debit processor 112, it isalso the utilized debit network 308. Accordingly, it is placed first inthe merchant routing table 602. Star is utilized over Pulse in therespective network subgroup, so it is above Pulse in the merchantrouting table 602. However, as Interlink is the utilized debit network308 in instances where Star and Interlink are the first 302 and second304 debit networks, Interlink is ahead of star in the merchant routingtable 602.

In some embodiments, the processing unit 204 may be configured toidentify a merchant routing table 602 for multiple transaction dates312. For example, the processing unit 204 may identify merchant routingtables 602 for each of four consecutive transaction dates 312, asillustrated in FIG. 7 as merchant routing tables 602 a, 602 b, 602 c,and 602 d. In the illustrated example, the processing unit 204 mayidentify that the merchant routing table 602 c is different from themerchant routing table 602 b. Accordingly, the processing unit 204 mayidentify that the merchant 108 changed their routing table on Jul. 5,2012 by moving Star to the top of the routing table 602. Methods foridentifying a specific date when a merchant routing table is changedwill be apparent to persons having skill in the relevant art.

In embodiments where one or more network subgroups 504 of the pluralityof network subgroups 502 include a third debit network 306 (e.g., ormore), the processing unit 204 may apply an algorithm or use methodsknown in the art to identify the order of the merchant routing table602. For example, if a network subgroup 504 includes financialtransactions involving debit cards 104 with four eligible debitprocessors 112, such as Maestro, Interlink, Star, and Pulse, then theprocessing unit 204 may identify the utilized debit network 308 ashaving preference over the other three debit processors 112. Theprocessing unit may decompose the relationship into multiple comparisonsof two networks, such as, for example, Maestro>Interlink, Maestro>Star,and Maestro>Pulse if Maestro is the utilized debit network 308. Theprocessing unit 204 may then apply known rules, such as the trianglerule (e.g., if A>B and B>C, then A>C) once all relationships have beendecomposed to identify the merchant routing table 602.

First Exemplary Method for Identifying a Merchant Debit Routing Table

FIG. 8 illustrates a first exemplary method 800 for identifying amerchant debit routing table (e.g., the routing table 602) using thesystem 100.

In step 802, a plurality of transaction data entries (e.g., transactiondata entries 120) may be stored in a database (e.g., the transactiondatabase 118), wherein each transaction data entry 120 includes datarelated to a financial transaction and includes at least a first debitnetwork (e.g., the first debit network 302), a second debit network(e.g., the second debit network 304), a utilized debit network (e.g.,the utilized debit network 308), a merchant identifier (e.g., themerchant identifier 310), and a transaction date (e.g., the transactiondate 312), the utilized debit network 308 being the first debit network302 or the second debit network 304. In some embodiments, the merchantidentifier 310 may be a merchant identification number (MID).

In step 804, a routing identification request may be received, by areceiving device (e.g., the receiving unit 202), wherein the routingidentification request includes at least a merchant identification. Instep 806, a merchant transaction group (e.g., the merchant transactiongroup 404) may be identified by a processing device (e.g., theprocessing unit 204), wherein the merchant transaction group 404includes transaction data entries 120 of the plurality of transactiondata entries 120 where the included merchant identifier 310 correspondsto the merchant identification.

In step 808, a plurality of network subgroups (e.g., the plurality ofnetwork subgroups 502) may be identified, by the processing device 204,in the merchant transaction group 404, wherein each network subgroup(e.g., the network subgroup 504) includes transaction data entries 120included in the merchant transaction group 404 including a common firstdebit network 302 and a common second debit network 304. In oneembodiment, each transaction data entry 120 may further include atransaction amount category (e.g., the transaction amount 312) of aplurality of transaction amount categories, and each network subgroup504 may include transaction data entries 120 further including commontransaction amount categories.

In step 810, a preferred debit network may be identified for eachnetwork subgroup 504 of the plurality of network subgroups 502 based onthe utilized debit network 308 for each transaction data entry 120 inthe network subgroup 504 where the transaction date 312 is a specificdate. In one embodiment, the routing identification request may furtherinclude the specific date.

In step 812, a routing table (e.g., the routing table 602) may beidentified, by the processing device 204, for a merchant (e.g., themerchant 108) associated with the merchant identifier 310 based on thepreferred debit network and the first debit network 302 and the seconddebit network 304 for each network subgroup 502 of the plurality ofnetwork subgroups 504. In embodiments where each network subgroup 504may further include a common transaction amount category, step 812 mayfurther include identifying a routing table 602 for each transactionamount category of the plurality of transaction amount categories.

In some embodiments, at least one transaction data entry 120 may includea third debit network (e.g., the third debit network 306). In such anembodiment, identifying the plurality of network subgroups 502 mayfurther include each network subgroup 504 including transaction dataentries 120 included in the merchant transaction group 404 including acommon first, second, and third debit network. Identifying a routingtable 602 may also further include identifying a routing table 602 basedon the preferred debit network and the first, second, and third debitnetworks for each network subgroup 504 of the plurality of networksubgroups 502.

Second Exemplary Method for Identifying a Merchant Debit Routing Table

FIG. 9 illustrates a first exemplary method 900 for identifying amerchant debit routing table (e.g., the routing table 602) using thesystem 100.

In step 902, a plurality of transaction data entries (e.g., transactiondata entries 120) may be stored in a database (e.g., the transactiondatabase 118), wherein each transaction data entry 120 includes datarelated to a financial transaction and includes at least a first debitnetwork (e.g., the first debit network 302), a second debit network(e.g., the second debit network 304), a utilized debit network (e.g.,the utilized debit network 308), a merchant identifier (e.g., themerchant identifier 310), and a transaction date (e.g., the transactiondate 312), the utilized debit network 308 being the first debit network302 or the second debit network 304. In some embodiments, the merchantidentifier 310 may be a merchant identification number (MID).

In step 904, a routing identification request may be received, by areceiving device (e.g., the receiving unit 202), wherein the routingidentification request includes at least a merchant identification. Instep 806, a merchant transaction group (e.g., the merchant transactiongroup 404) may be identified by a processing device (e.g., theprocessing unit 204), wherein the merchant transaction group 404includes transaction data entries 120 of the plurality of transactiondata entries 120 where the included merchant identifier 310 correspondsto the merchant identification.

In step 908, a plurality of network subgroups (e.g., the plurality ofnetwork subgroups 502) may be identified, by the processing device 204,in the merchant transaction group 404, wherein each network subgroup(e.g., the network subgroup 504) includes transaction data entries 120included in the merchant transaction group 404 including a common firstdebit network 302 and a common second debit network 304. In oneembodiment, each transaction data entry 120 may further include atransaction amount category (e.g., the transaction amount 312) of aplurality of transaction amount categories, and each network subgroup504 may include transaction data entries 120 further including commontransaction amount categories.

In step 910, a preferred debit network may be identified for eachnetwork subgroup 504 of the plurality of network subgroups 502 for eachdate of a predetermined range of dates, based on the utilized debitnetwork 308 for each transaction data entry 120 in the network subgroup504 where the transaction date 312 corresponds to the respective date inthe predetermined range of dates. In some embodiments, the routingidentification request may further include the predetermined range ofdates.

In step 912, a routing table (e.g., the routing table 602) may beidentified, by the processing device 204, for a merchant (e.g., themerchant 108) associated with the merchant identifier 310 for each dateof the predetermined range of dates, based on the preferred debitnetwork and the first debit network 302 and the second debit network 304for each network subgroup 502 of the plurality of network subgroups 504for the respective date of the predetermined range of dates. Inembodiments where each network subgroup 504 may further include a commontransaction amount category, step 912 may further include identifying arouting table 602 for each transaction amount category of the pluralityof transaction amount categories.

In step 914, a change in debit routing for the merchant 108 may beidentified, by the processing device 204, based on the routing table 602for the merchant 108 for each date of the predetermined range of dates.In some embodiments, at least one transaction data entry 120 may includea third debit network (e.g., the third debit network 306). In such anembodiment, identifying the plurality of network subgroups 502 mayfurther include each network subgroup 504 including transaction dataentries 120 included in the merchant transaction group 404 including acommon first, second, and third debit network. Identifying a routingtable 602 may also further include identifying a routing table 602 basedon the preferred debit network and the first, second, and third debitnetworks for each network subgroup 504 of the plurality of networksubgroups 502.

Computer System Architecture

FIG. 10 illustrates a computer system 1000 in which embodiments of thepresent disclosure, or portions thereof, may be implemented ascomputer-readable code. For example, the issuer 106, the merchant 108,the debit processors 112, and the processing server 114 of FIG. 1 may beimplemented in the computer system 1000 using hardware, software,firmware, non-transitory computer readable media having instructionsstored thereon, or a combination thereof and may be implemented in oneor more computer systems or other processing systems. Hardware,software, or any combination thereof may embody modules and componentsused to implement the methods of FIGS. 8 and 9.

If programmable logic is used, such logic may execute on a commerciallyavailable processing platform or a special purpose device. A personhaving ordinary skill in the art may appreciate that embodiments of thedisclosed subject matter can be practiced with various computer systemconfigurations, including multi-core multiprocessor systems,minicomputers, mainframe computers, computers linked or clustered withdistributed functions, as well as pervasive or miniature computers thatmay be embedded into virtually any device. For instance, at least oneprocessor device and a memory may be used to implement the abovedescribed embodiments.

A processor device as discussed herein may be a single processor, aplurality of processors, or combinations thereof. Processor devices mayhave one or more processor “cores.” The terms “computer program medium,”“non-transitory computer readable medium,” and “computer usable medium”as discussed herein are used to generally refer to tangible media suchas a removable storage unit 1018, a removable storage unit 1022, and ahard disk installed in hard disk drive 1012.

Various embodiments of the present disclosure are described in terms ofthis example computer system 1000. After reading this description, itwill become apparent to a person skilled in the relevant art how toimplement the present disclosure using other computer systems and/orcomputer architectures. Although operations may be described as asequential process, some of the operations may in fact be performed inparallel, concurrently, and/or in a distributed environment, and withprogram code stored locally or remotely for access by single ormultiprocessor machines. In addition, in some embodiments the order ofoperations may be rearranged without departing from the spirit of thedisclosed subject matter.

Processor device 1004 may be a special purpose or a general purposeprocessor device. The processor device 1004 may be connected to acommunication infrastructure 1006, such as a bus, message queue,network, multi-core message-passing scheme, etc. The network may be anynetwork suitable for performing the functions as disclosed herein andmay include a local area network (LAN), a wide area network (WAN), awireless network (e.g., WiFi), a mobile communication network, asatellite network, the Internet, fiber optic, coaxial cable, infrared,radio frequency (RF), or any combination thereof. Other suitable networktypes and configurations will be apparent to persons having skill in therelevant art. The computer system 1000 may also include a main memory1008 (e.g., random access memory, read-only memory, etc.), and may alsoinclude a secondary memory 1010. The secondary memory 1010 may includethe hard disk drive 1012 and a removable storage drive 1014, such as afloppy disk drive, a magnetic tape drive, an optical disk drive, a flashmemory, etc.

The removable storage drive 1014 may read from and/or write to theremovable storage unit 1018 in a well-known manner. The removablestorage unit 1018 may include a removable storage media that may be readby and written to by the removable storage drive 1014. For example, ifthe removable storage drive 1014 is a floppy disk drive, the removablestorage unit 1018 may be a floppy disk. In one embodiment, the removablestorage unit 1018 may be non-transitory computer readable recordingmedia.

In some embodiments, the secondary memory 1010 may include alternativemeans for allowing computer programs or other instructions to be loadedinto the computer system 1000, for example, the removable storage unit1022 and an interface 1020. Examples of such means may include a programcartridge and cartridge interface (e.g., as found in video gamesystems), a removable memory chip (e.g., EEPROM, PROM, etc.) andassociated socket, and other removable storage units 1022 and interfaces1020 as will be apparent to persons having skill in the relevant art.

Data stored in the computer system 1000 (e.g., in the main memory 1008and/or the secondary memory 1010) may be stored on any type of suitablecomputer readable media, such as optical storage (e.g., a compact disc,digital versatile disc, Blu-ray disc, etc.) or magnetic tape storage(e.g., a hard disk drive). The data may be configured in any type ofsuitable database configuration, such as a relational database, astructured query language (SQL) database, a distributed database, anobject database, etc. Suitable configurations and storage types will beapparent to persons having skill in the relevant art.

The computer system 1000 may also include a communications interface1024. The communications interface 1024 may be configured to allowsoftware and data to be transferred between the computer system 1000 andexternal devices. Exemplary communications interfaces 1024 may include amodem, a network interface (e.g., an Ethernet card), a communicationsport, a PCMCIA slot and card, etc. Software and data transferred via thecommunications interface 1024 may be in the form of signals, which maybe electronic, electromagnetic, optical, or other signals as will beapparent to persons having skill in the relevant art. The signals maytravel via a communications path 1026, which may be configured to carrythe signals and may be implemented using wire, cable, fiber optics, aphone line, a cellular phone link, a radio frequency link, etc.

Computer program medium and computer usable medium may refer tomemories, such as the main memory 1008 and secondary memory 1010, whichmay be memory semiconductors (e.g. DRAMs, etc.). These computer programproducts may be means for providing software to the computer system1000. Computer programs (e.g., computer control logic) may be stored inthe main memory 1008 and/or the secondary memory 1010. Computer programsmay also be received via the communications interface 1024. Suchcomputer programs, when executed, may enable computer system 1000 toimplement the present methods as discussed herein. In particular, thecomputer programs, when executed, may enable processor device 1004 toimplement the methods illustrated by FIGS. 8 and 9, as discussed herein.Accordingly, such computer programs may represent controllers of thecomputer system 1000. Where the present disclosure is implemented usingsoftware, the software may be stored in a computer program product andloaded into the computer system 1000 using the removable storage drive1014, interface 1020, and hard disk drive 1012, or communicationsinterface 1024.

Techniques consistent with the present disclosure provide, among otherfeatures, systems and methods for the identification of merchant debitrouting tables. While various exemplary embodiments of the disclosedsystem and method have been described above it should be understood thatthey have been presented for purposes of example only, not limitations.It is not exhaustive and does not limit the disclosure to the preciseform disclosed. Modifications and variations are possible in light ofthe above teachings or may be acquired from practicing of thedisclosure, without departing from the breadth or scope.

What is claimed is:
 1. A method for identifying a merchant debit routing table, comprising: storing, in a database, a plurality of transaction data entries, wherein each transaction data entry includes data related to a payment transaction and includes at least a first debit network, a second debit network, a utilized debit network, and a merchant identifier, the utilized debit network being the first debit network or the second debit network; identifying, by a processing device, a subset of the plurality of transaction data entries, wherein each transaction data entry in the subset includes a specific merchant identifier; identifying, by the processing device, a plurality of network subgroups in the subset of the plurality of transaction data entries, wherein each network subgroup includes transaction data entries included in the subset includes a common first debit network and a common second debit network; identifying, for each network subgroup of the plurality of network subgroups, a preferred debit network based on the utilized debit network for each transaction data entry in the network subgroup; and identifying, by the processing device, a routing table for a merchant associated with the specific merchant identifier based on the preferred debit network and the first debit network and the second debit network for each network subgroup of the plurality of network subgroups.
 2. The method of claim 1, wherein the merchant identifier is a merchant identification number (MID).
 3. The method of claim 1, wherein each transaction data entry further includes a transaction amount category of a plurality of transaction amount categories, and identifying a plurality of network subgroups further includes identifying a plurality network subgroups where each network subgroup includes transaction data entries included in the subset including a common first debit network, a common second debit network, and a common transaction amount category.
 4. The method of claim 3, wherein identifying a routing table includes identifying a routing table for the merchant associated with the merchant identifier for each transaction amount category of the plurality of transaction amount categories.
 5. The method of claim 1, wherein each transaction data entry further includes a third debit network, identifying a plurality of network subgroups further includes identifying a plurality network subgroups where each network subgroup includes transaction data entries included in the subset including a common first debit network, a common second debit network, and a common third debit network, and identifying a routing table includes identifying a routing table based on the preferred debit network and the first debit network, the second debit network, and the third debit network for each network subgroup of the plurality of network subgroups.
 6. A method for identifying a change in a merchant routing table, comprising: storing, in a database, a plurality of transaction data entries, wherein each transaction data entry includes data related to a financial transaction and includes at least a first debit network, a second debit network, a utilized debit network, a merchant identifier, and a transaction date, the utilized debit network being the first debit network or the second debit network; identifying, by a processing device, a subset of the plurality of transaction data entries, wherein each transaction data entry in the subset includes a specific merchant identifier; identifying, by the processing device, a plurality of network subgroups in the subset of the plurality of transaction data entries, wherein each network subgroup includes transaction data entries included in the subset includes a common first debit network and a common second debit network; identifying, for each date of a predetermined range of dates, a preferred debit network for each network subgroup of the plurality of network subgroups based on the utilized debit network for each transaction data entry in the respective network subgroup where the transaction date corresponds to the respective date in the predetermined range of dates; identifying, for each date of the predetermined range of dates, a routing table for a merchant associated with the specific merchant identifier based on the preferred debit network and the first debit network and the second debit network for each network subgroup of the plurality of network subgroups for the respective date of the predetermined range of dates; and identifying, by the processing device, a change in debit routing for the merchant based on the routing table for the merchant for each date of the predetermined range of dates.
 7. The method of claim 6, wherein the routing identification request further includes the predetermined range of dates.
 8. The method of claim 6, wherein the merchant identifier 310 is a merchant identification number (MID).
 9. The method of claim 6, wherein each transaction data entry further includes a transaction amount category of a plurality of transaction amount categories, and identifying a plurality of network subgroups further includes identifying a plurality network subgroups where each network subgroup includes transaction data entries included in the subset including a common first debit network, a common second debit network, and a common transaction amount category.
 10. The method of claim 9, wherein identifying a routing table includes identifying a routing table for the merchant associated with the specific merchant identifier for each transaction amount category of the plurality of transaction amount categories.
 11. The method of claim 10, wherein identifying a change in debit routing for the merchant includes identifying a change in debit routing for the merchant based on the routing table for the merchant for each transaction amount category of the plurality of transaction amount categories for each date of the predetermined range of dates
 12. The method of claim 6, wherein each transaction data entry further includes a third debit network, identifying a plurality of network subgroups further includes identifying a plurality network subgroups where each network subgroup includes transaction data entries included in the subset including a common first debit network, a common second debit network, and a common third debit network, and identifying a routing table includes identifying a routing table based on the preferred debit network and the first debit network, the second debit network, and the third debit network for each network subgroup of the plurality of network subgroups.
 13. A method for identifying a merchant debit routing table, comprising: storing, in a database, a plurality of transaction data entries, wherein each transaction data entry includes data related to a payment transaction involving a common merchant and includes at least a first debit network, a second debit network, and a utilized debit network, the utilized debit network being the first debit network or the second debit network; identifying, by a processing device, a plurality of subsets of the plurality of transaction data entries, wherein each transaction data entry included in each respective subset includes a common first debit network and a common second debit network; and identifying, by the processing device, a routing table for the common merchant based on a preferred debit network for each of the plurality of subsets of the plurality of transaction data entries based on the utilized debit network and the common first debit network and common second debit network for each transaction data entry included in each of the respective subsets.
 14. The method of claim 13, wherein each transaction data entry further includes a transaction amount category of a plurality of transaction amount categories, and identifying a plurality of subsets further includes identifying a plurality of subsets of the plurality of transaction data entries where each transaction data entry included in each respective subset includes a common first debit network, a common second debit network, and a common transaction amount category.
 15. The method of claim 14, wherein identifying a routing table includes identifying a routing table for the common merchant for each transaction amount category of the plurality of transaction amount categories.
 16. The method of claim 13, wherein each transaction data entry further includes a third debit network, identifying a plurality of subsets further includes identifying a plurality of subsets of the plurality of transaction data entries where each transaction data entry included in each respective subset includes a common first debit network, a common second debit network, and a common third debit network, and identifying a routing table includes identifying a routing table for the common merchant based on a preferred debit network for each of the plurality of subsets of the plurality of transaction data entries based on the utilized debit network and the common first debit network, common second debit network, and common third debit network for each transaction data entry included in each of the respective subsets.
 17. The method of claim 13, wherein each transaction data entry further includes a specific date of a predetermined range of dates, and identifying a plurality of subsets further includes identifying a plurality of subsets of the plurality of transaction data entries where each transaction data entry included in each respective subset includes a common first debit network, a common second debit network, and a common specific date.
 18. The method of claim 17, wherein identifying a routing table includes identifying a routing table for the common merchant for each specific date of the predetermined range of dates.
 19. The method of claim 18, further comprising: identifying, by the processing device, a change in debit routing for the common merchant based on the identified routing table for each specific date of the predetermined range of dates.
 20. A system for identifying a merchant debit routing table, comprising: a database configured to store a plurality of transaction data entries, wherein each transaction data entry includes data related to a payment transaction and includes at least a first debit network, a second debit network, a utilized debit network, and a merchant identifier, the utilized debit network being the first debit network or the second debit network; and a processing device configured to identify a subset of the plurality of transaction data entries, wherein each transaction data entry in the subset includes a specific merchant identifier, identify a plurality of network subgroups in the subset of the plurality of transaction data entries, wherein each network subgroup includes transaction data entries included in the subset includes a common first debit network and a common second debit network, identify, for each network subgroup of the plurality of network subgroups, a preferred debit network based on the utilized debit network for each transaction data entry in the network subgroup, and identify a routing table for a merchant associated with the specific merchant identifier based on the preferred debit network and the first debit network and the second debit network for each network subgroup of the plurality of network subgroups.
 21. The system of claim 20, wherein the merchant identifier is a merchant identification number (MID).
 22. The system of claim 20, wherein each transaction data entry further includes a transaction amount category of a plurality of transaction amount categories, and identifying a plurality of network subgroups further includes identifying a plurality network subgroups where each network subgroup includes transaction data entries included in subset including a common first debit network, a common second debit network, and a common transaction amount category.
 23. The system of claim 20, wherein identifying a routing table includes identifying a routing table for the merchant associated with the merchant identifier for each transaction amount category of the plurality of transaction amount categories.
 24. The system of claim 20, wherein each transaction data entry further includes a third debit network, identifying a plurality of network subgroups further includes identifying a plurality network subgroups where each network subgroup includes transaction data entries included in the subset including a common first debit network, a common second debit network, and a common third debit network, and identifying a routing table includes identifying a routing table based on the preferred debit network and the first debit network, the second debit network, and the third debit network for each network subgroup of the plurality of network subgroups.
 25. A system for identifying a change in a merchant routing table, comprising: a database configured to store a plurality of transaction data entries, wherein each transaction data entry includes data related to a financial transaction and includes at least a first debit network, a second debit network, a utilized debit network, a merchant identifier, and a transaction date, the utilized debit network being the first debit network or the second debit network; and a processing device configured to identify a subset of the plurality of transaction data entries, wherein each transaction data entry in the subset includes a specific merchant identifier, identify a plurality of network subgroups in the subset of the plurality of transaction data entries, wherein each network subgroup includes transaction data entries included in the subset includes a common first debit network and a common second debit network, identify, for each date of a predetermined range of dates, a preferred debit network for each network subgroup of the plurality of network subgroups based on the utilized debit network for each transaction data entry in the respective network subgroup where the transaction date corresponds to the respective date in the predetermined range of dates, identify, for each date of the predetermined range of dates, a routing table for a merchant associated with the specific merchant identifier based on the preferred debit network and the first debit network and the second debit network for each network subgroup of the plurality of network subgroups for the respective date of the predetermined range of dates, and identify a change in debit routing for the merchant based on the routing table for the merchant for each date of the predetermined range of dates.
 26. The system of claim 25, wherein the routing identification request further includes the predetermined range of dates.
 27. The system of claim 25, wherein the merchant identifier is a merchant identification number (MID).
 28. The system of claim 25, wherein each transaction data entry further includes a transaction amount category of a plurality of transaction amount categories, and identifying a plurality of network subgroups further includes identifying a plurality network subgroups where each network subgroup includes transaction data entries included in the subset including a common first debit network, a common second debit network, and a common transaction amount category.
 29. The system of claim 28, wherein identifying a routing table includes identifying a routing table for the merchant associated with the specific merchant identifier for each transaction amount category of the plurality of transaction amount categories.
 30. The system of claim 29, wherein identifying a change in debit routing for the merchant includes identifying a change in debit routing for the merchant based on the routing table for the merchant for each transaction amount category of the plurality of transaction amount categories for each date of the predetermined range of dates
 31. The system of claim 25, wherein each transaction data entry further includes a third debit network, identifying a plurality of network subgroups further includes identifying a plurality network subgroups where each network subgroup includes transaction data entries included in the subset including a common first debit network, a common second debit network, and a common third debit network, and identifying a routing table includes identifying a routing table based on the preferred debit network and the first debit network, the second debit network, and the third debit network for each network subgroup of the plurality of network subgroups.
 32. A system for identifying a merchant debit routing table, comprising: a database configured to store a plurality of transaction data entries, wherein each transaction data entry includes data related to a payment transaction involving a common merchant and includes at least a first debit network, a second debit network, and a utilized debit network, the utilized debit network being the first debit network or the second debit network; and a processing device configured to identify a plurality of subsets of the plurality of transaction data entries, wherein each transaction data entry included in each respective subset includes a common first debit network and a common second debit network, and identify, a routing table for the common merchant based on a preferred debit network for each of the plurality of subsets of the plurality of transaction data entries based on the utilized debit network and the common first debit network and common second debit network for each transaction data entry included in each of the respective subsets.
 33. The system of claim 32, wherein each transaction data entry further includes a transaction amount category of a plurality of transaction amount categories, and identifying a plurality of subsets further includes identifying a plurality of subsets of the plurality of transaction data entries where each transaction data entry included in each respective subset includes a common first debit network, a common second debit network, and a common transaction amount category.
 34. The system of claim 33, wherein identifying a routing table includes identifying a routing table for the common merchant for each transaction amount category of the plurality of transaction amount categories.
 35. The system of claim 32, wherein each transaction data entry further includes a third debit network, identifying a plurality of subsets further includes identifying a plurality of subsets of the plurality of transaction data entries where each transaction data entry included in each respective subset includes a common first debit network, a common second debit network, and a common third debit network, and identifying a routing table includes identifying a routing table for the common merchant based on a preferred debit network for each of the plurality of subsets of the plurality of transaction data entries based on the utilized debit network and the common first debit network, common second debit network, and common third debit network for each transaction data entry included in each of the respective subsets.
 36. The system of claim 32, wherein each transaction data entry further includes a specific date of a predetermined range of dates, and identifying a plurality of subsets further includes identifying a plurality of subsets of the plurality of transaction data entries where each transaction data entry included in each respective subset includes a common first debit network, a common second debit network, and a common specific date.
 37. The system of claim 36, wherein identifying a routing table includes identifying a routing table for the common merchant for each specific date of the predetermined range of dates.
 38. The system of claim 37, further comprising: identifying, by the processing device, a change in debit routing for the common merchant based on the identified routing table for each specific date of the predetermined range of dates. 